@TG1999 I've just committed and pushed my latest code (still a w-i-p) with updates to postgresql.py and test_postgresql.py. I'm also uploading 2 related .txt files:

• 2022-10-28-postgresql.py-to_advisories()-print-statements.txt -- copy of postgresql.py to_advisories() print statements triggered by the skeletal test_to_advisories_simple test
• 2022-10-28-postgresql.py-to_advisories()-print-statements-advisories-object.txt -- the advisories object from the print statements, plus a manual effort to partially extract/display the structure of the advisories object

Here are the 2 files.
2022-10-28-postgresql.py-to_advisories()-print-statements.txt
2022-10-28-postgresql.py-to_advisories()-print-statements-advisories-object.txt

@TG1999 Note that I am separating the individual packages (AffectedPackage objects) in each table row by using the count of versions listed in the Affected column, pairing each version with the corresponding version in the Fixed column, and assuming that this pairing is correct and reliable. It does seem a bit "fragile" to me -- perhaps there's a better approach?

@TG1999 I have been unable to find any licensing information on the PostgreSQL security pages. The primary license reference is at https://www.postgresql.org/about/licence/, which identifies the applicable license as "the PostgreSQL License", with a link to https://www.opensource.org/licenses/postgresql.

By its terms, this license covers "this software and its documentation", which could be interpreted to include security-related information within the definition of "documentation". That is the approach I am taking, subject to your input and input from other colleagues. Accordingly, I have updated the license-related info near the top of postgresql.py to read as follows:

    root_url = "https://www.postgresql.org/support/security/"
    license_url = "https://www.postgresql.org/about/licence/"
    spdx_license_expression = "PostgreSQL"

@johnmhoran the changes look good to me, please add a CHANGELOG entry for same.

@TG1999 On my local branch 969-migrate-postgresql-importer the top of the changelog looks like this:

Version v30.2.2
----------------

- We enabled API throttling for a basic user and for a staff user 
  they can have unlimited access on API.

- We added throttle rate for each API endpoint and it can be 
  configured from the settings #991 https://github.com/nexB/vulnerablecode/issues/991.

Version v30.2.1
----------------

- We refactored and fixed the LaunchPad API code.
- We now ignore qualifiers and subpath from PURL search lookups.
- We fixed severity table column spillover.

In the main branch the top of the changelog looks like this:

Version v30.3.1
This is a minor bug fix release.

We enabled proper CSRF configuration for deployments

Do I add the changelog entry (e.g., We re-enabled support for PostgreSQL securities advisories importer.) under Version v30.2.2, or do I update main, rebase main on my branch, and then add the changelog entry under a new Version v30.3.2 heading (and then force push the commit)? Or something different?

rebase main on my branch, and then add the changelog entry under a new Version v30.3.2 heading (and then force push the commit)

@johnmhoran please do this.

@TG1999 Updated/pushed as discussed -- all GH checks have passed.

This likely needs a small adjustment for the new CVSS processing

Thanks @johnmhoran for your PR, I have regen the tests and all tests are passing now.